Re: authentication problems - Mailing list pgsql-admin

From Russ McBride
Subject Re: authentication problems
Date
Msg-id v04210103b7dc469a6205@[64.170.120.144]
Whole thread Raw
In response to Re: authentication problems  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: authentication problems  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Typing "/usr/local/pgsql/bin/psql -h localhost testdb" starts up my
database in psql quite nicely, which seems to indicate to me that the
pg_hba.conf is being read and the line:

local  all                        trust
is working as expected (I assume that this is the line that allows
all local UNIX socket connections).

Hmmm.  Perhaps the host line working fine for ip connections as well,
but something is going wrong in the JDBC-specific ip connections.  Is
there a way to make a local ip connection instead of a UNIX socket
connection with psql?

best,

Russ





>Russ McBride <Russ@psyex.com> writes:
> > I typed "/usr/local/pgsql/bin/psql -h localhost" and
> > "/usr/local/pgsql/bin/psql -h 127.0.0.1" and they both returned the
> > same (odd) message:
>
> > psql: FATAL 1: database "postgres" does not exist in the system catalog
>
>Nothing odd about that: the database name is defaulting to your PG user
>name, evidently postgres.  Try "psql -h localhost databasename" for
>some valid database name.  The important thing about this message is
>that you are getting past the pg_hba.conf check, so this *is* forward
>progress.
>
>            regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: authentication problems
Next
From: Tom Lane
Date:
Subject: Re: authentication problems